Skip to content

Add STM32F303VDxx and STM32F303VExx Variants#3016

Open
jamesrlucas wants to merge 1 commit into
stm32duino:mainfrom
jamesrlucas:add_f303ve_variants
Open

Add STM32F303VDxx and STM32F303VExx Variants#3016
jamesrlucas wants to merge 1 commit into
stm32duino:mainfrom
jamesrlucas:add_f303ve_variants

Conversation

@jamesrlucas

Copy link
Copy Markdown

Summary

  • Add STM32F303DExx and STM32VExx variants to boards.txt
  • Add missing ldscript to correct variants folder for above processor variants

This PR fixes/implements the following bugs/features

Adds support for new processors, currently missing from the 'Board Part Number' Menu

Validation

  • Variants now appear in 'Board Part Number' menu
  • Blinky sketch has been tested with a STM32F303VET6 processor

Closing issues

closes #3013

@fpistm fpistm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR.
Please, reference new mcu support in the README.md.

Comment thread boards.txt Outdated
@fpistm fpistm added the new variant Add support of new bard label Jul 7, 2026
@fpistm fpistm added this to the 3.0.0 milestone Jul 7, 2026
@github-project-automation github-project-automation Bot moved this from In progress to Needs review in STM32 core based on ST HAL Jul 7, 2026
@github-project-automation github-project-automation Bot moved this from Needs review to Reviewer approved in STM32 core based on ST HAL Jul 7, 2026
@jamesrlucas jamesrlucas marked this pull request as draft July 7, 2026 16:02
@jamesrlucas

Copy link
Copy Markdown
Author

I'm also looking at the generic_clock.c file (I didn't change it before, so was running at the default) but I have a question:

On the wiki, it states use the HSI for the PLL Mux, however doing this in CubeMX, it tells me PLL Source Mux must use HSE as input - what do I do here?

This is the clock config so far :
20260707_173756

@jamesrlucas jamesrlucas requested a review from fpistm July 7, 2026 17:11
@fpistm

fpistm commented Jul 7, 2026

Copy link
Copy Markdown
Member

It is an advice when you configure the USB. HSE is more stable.

@jamesrlucas

Copy link
Copy Markdown
Author

Okay, so I've tried that, and the code that it generates doesn't work - the processor doesn't appear to run

If I disable the USB, the generated clock init code works fine. I'll look at creating the usb clock init manually, instead of using cubeMX

@fpistm fpistm changed the title Add STM32F303DExx and STM32VExx Variants Add STM32F303VDxx and STM32F303VExx Variants Jul 8, 2026
Signed-off-by: James <james@jlucas.me.uk>
@fpistm fpistm force-pushed the add_f303ve_variants branch from a4b67a6 to 0b19c7f Compare July 8, 2026 06:54
@fpistm

fpistm commented Jul 8, 2026

Copy link
Copy Markdown
Member

Hi @jamesrlucas
Thanks for the update.
I don't see any issue in your clock config and don't know why it does not work.
Maybe using HSI with USB enabled leads to an issue.

I've updated your branch: squash all commit and apply astyle so think to fetch it before doing any other modifications.

@fpistm fpistm marked this pull request as ready for review July 8, 2026 06:57
@jamesrlucas

Copy link
Copy Markdown
Author

I've found the issue with the clock - CubeMX is missing the RCC Oscillator initialization steps if I generate the code with the internal oscillator as the USB source (as per the screenshot above) - Clearly it doesn't like the USB + HSI option...

Disabling the USB interface in CubeMX generates a working clock config, I'm using this currently for my project.
Enabling the external oscillator also generates what looks to be a working clock config, but I haven't tested this yet.

Will test this further and commit a clock config when I get chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new variant Add support of new bard

Projects

Status: Reviewer approved

Development

Successfully merging this pull request may close these issues.

New variants for F303V(D-E)(H-T)

2 participants